Description

Update barman to 2.19 after the upstream docker image was landed in ubc/barman-docker@59f3874.

Barman itself contains these changes from 2.19 and 2.18:

Features

• Change barman diagnose output date format to ISO8601.
• Add Google Cloud Storage (GCS) support to barman cloud.
• Support current and latest recovery targets for the --target-tli option of barman recover.
• Add documentation for installation on SLES.
• Add snappy compression algorithm support in barman cloud (requires the optional python-snappy dependency).
• Allow Azure client concurrency parameters to be set when uploading WALs with barman-cloud-wal-archive.
• Add --tags option in barman cloud so that backup files and archived WALs can be tagged in cloud storage (aws and azure).
• Update the barman cloud exit status codes so that there is a dedicated code (2) for connectivity errors.
• Add the commands barman verify-backup and barman generate-manifest to check if a backup is valid.
• Add support for Azure Managed Identity auth in barman cloud which can be enabled with the --credential option.

Bug fixes

• barman-wal-archive --test now returns a non-zero exit code when an error occurs.
• Fix barman-cloud-check-wal-archive behaviour when -t option is used so that it exits after connectivity test.
• barman recover now continues when --no-get-wal is used and "get-wal" is not set in recovery_options.
• Fix barman show-servers --format=json ${server} output for inactive server.
• Check for presence of barman_home in configuration file.
• Passive barman servers will no longer store two copies of the tablespace data when syncing backups taken with backup_method = postgres.
• Change barman-cloud-check-wal-archive behavior when bucket does not exist.
• Ensure list-files output is always sorted regardless of the underlying filesystem.
• Man pages for barman-cloud-backup-keep, barman-cloud-backup-delete and barman-cloud-check-wal-archive added to Python packaging.

Issues

• fixes [barman] 2.19 available #617

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released